Might be easier to just stick #![rustfmt::skip] at the top of the file in question (and then remove the nix-specific exclusion)?

Not sure why all the parameters, where do these come from?

generated from rustfmt --print-config default rustfmt.toml

EDIT: Yeah after looking at the options, probably not worth just changing a couple of them. I just ran the command because I thought there was a reason we weren't using the #[rustfmt::skip] ? @gierens

I thought we had a rustfmt.toml file before anyway? Idk, could be useful at some point. but definitely got rid of all the options.

Might be easier to just stick #![rustfmt::skip] at the top of the file in question (and then remove the nix-specific exclusion)?

Seems like clippy doesn't like it. I'll see if I can find an alternative

Run cargo clippy -- -D warnings
   Compiling eza v0.13.1 (/home/runner/work/eza/eza)
error: custom inner attributes are unstable
 --> src/options/flags.rs:1:4
  |
1 | #![rustfmt::skip]
  |    ^^^^^^^^^^^^^
  |
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #64266 </~https://github.com/rust-lang/rust/issues/64266>
  = note: `#[deny(soft_unstable)]` on by default

error: could not compile `eza` (lib) due to previous error
Error: Process completed with exit code 101.

See: rust-lang/rust#64266

Huh, that's surprising. In that case I'd probably go for a rustfmt.toml with the one setting in it and get rid of the Nix-specific one so that things aren't at risk of going out of sync.

Huh, that's surprising. In that case I'd probably go for a rustfmt.toml with the one setting in it and get rid of the Nix-specific one so that things aren't at risk of going out of sync.

Yea, seems Nix respect the rustfmt one, so that seems like the correct way to handle this.

Was removing this was forgotten? Seems like it should be redundant with this change, no?

Was removing this was forgotten? Seems like it should be redundant with this change, no?

Yeop 🤦‍♀️

Turns out, it doesn't read the rustfmt.toml. What I thought was it reading it was actually it reading it through taplo...

Welp, guess we'll need to do it two places for now.